Mini-Form View for Data Records

ABSTRACT

Methods, program products, and systems for mini-form view of data records are described. Each data records can be formatted according to a layout. The layout can define an arrangement of various data fields for display. To display multiple data records, an image can be created for each formatted data record. Each image can be a snapshot of the formatted data record. The image can have a size that is smaller than the size of the layout. The arrangement of the data fields can be preserved in the image. Multiple images of formatted data records can be displayed in a single window. By displaying formatted data records in images, the “look and feel” in the layout of each data record can be preserved, even when multiple records are displayed. The mini-form view can display data records from multiple shared databases.

TECHNICAL FIELD

This disclosure relates generally to formatting data.

BACKGROUND

A modern database application program can provide graphical userinterfaces for visually displaying and editing data stored in adatabase. The data can be retrieved from the database as result sets(sometimes referred to as found sets) using one or more database queries(sometimes referred to as find requests). A result set can include acollection of data records. The data records in the result set can beformatted for display. For example, in a database program for auctions,a user can query for a particular item or category of items beingauctioned (e.g., “computers”). In response, the database program canreturn a result set containing data records on matching items. Each datarecord can correspond to a particular item. The data record cancorrespond to formatting information that specifies how the various datafields concerning the item (e.g., name, price, description, and pictureof the item) can be displayed on screen.

The user can view each item individually, or view multiple items in alist. When the user views an individual item, the display can beformatted using the corresponding formatting information. For example,the name, price, and description of a computer each can have a specificfont, display size, and color. The picture can be displayed at aparticular positioned on screen. In contrast, when the user viewsmultiple items on a display screen, the records can be arranged as atable or a list. Displaying the items in a table or a list can hide thecorresponding formatting information for the item. Therefore, viewingthe table or list of auction items, the user may not see how eachauction item will be presented when displayed individually.

SUMMARY

Methods, program products, and systems for mini-form view of datarecords are described. Each of the data records can be formatted fordisplay according to a layout. The layout can define an arrangement ofvarious data fields (including images) for display. To display multipledata records, an image (e.g., a mini-sized form, or mini-form) can becreated for each formatted data record. Each image can be a snapshot ofthe formatted data record. The image can have a size that is smallerthan the size specified in the layout. However, the arrangement of thedata fields in the layout can be preserved in the image. The arrangementcan be scaled according to the size of the image, which can beadjustable. Multiple images of formatted data records can be displayedin a single window. By displaying formatted data records in images, the“look and feel” in the layout of each data record can preserved, evenwhen multiple records are displayed. The multiple images can bedisplayed in a display pattern (e.g., a grid). The mini-form view candisplay data records from multiple shared databases.

In some implementations, various display items, including images offormatted data records, can be put in a library. The display items inthe library can be organized into a hierarchical structure (e.g., afolder and sub-folder structure) having various levels. A user canbrowse the display items by navigating a source list, which canvisualize the hierarchical structure. When the user selects a level, thedisplay items at that level can be displayed. If one of the items beingdisplayed (e.g., a folder) contains other display items of a lower level(e.g., mini-forms in the folder), the lower-level display items can bedisplayed in animation. Upon a user selection of the item (e.g.,selecting the folder), the display can be animated to cycle through eachof the items contained in the folder. The animation can occur in thedisplay area occupied by the selected item. The user selection caninclude, for example, a movement of a pointer across the displayedfolder. The user can view details of a particular display item by makinga second selection to select that display item (e.g., by clicking on thedisplay item when the item is being displayed according to the cycle).

Techniques for presenting mini-form view for data records can beimplemented to achieve the following exemplary advantages. A databaseapplication user can view results in grid mode, as well as other modes.In grid mode, multiple database query results can be displayed on asingle page as mini-forms, while the formatting of each result ispreserved. The user can view a mini-form of a formatted query result inarbitrary size. Changes in a data record in one mini-form can bereflected in all the mini-forms. The user can browse database queryresults side by side with other content (e.g., images, video clips, ordocuments). The user can view multiple levels of display content in oneor more animations on one display device. Each animation can beindependent of another animation. As such, multiple levels of contentcan be displayed in single display window. The user can manipulatedisplay items in arbitrary numbers of levels.

The details of one or more implementations of mini-form view for datarecords are set forth in the accompanying drawings and the descriptionbelow. Other features, aspects, and advantages of mini-form view fordata records will become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an exemplary mini-form view of images of formatteddata records.

FIG. 1B illustrates an exemplary mini-form view of images of formatteddata records where one data record is selected for editing.

FIGS. 2A-2C illustrate exemplary mini-form views of images of formatteddata records that are organized in a hierarchical structure.

FIG. 2D illustrates an exemplary mini-form view of images of datarecords in shared databases.

FIGS. 3A-3C illustrate exemplary user interfaces for configuring amini-form view display of images data records.

FIG. 4A illustrates an exemplary mini-form view of images of datarecords together with other content.

FIG. 4B illustrates an exemplary user interface for creating a libraryof images of data records from a mini-form view.

FIG. 5A is a flowchart illustrating an exemplary process of displayingdata records in mini-form view.

FIG. 5B is a flowchart illustrating an exemplary process of displayingimages of data records that are organized in a hierarchical structure.

FIGS. 5C-5F illustrate exemplary display patterns of images of formatteddata records.

FIG. 6 is a block diagram of an exemplary system architecture forimplementing the features and operations described in reference to FIGS.1-5.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION Mini-Form View for Data Records Overview

FIG. 1A illustrates an exemplary mini-form view 100 of images offormatted data records. For convenience, user interface 100 will bedescribed with reference to an application program that implements userinterface 100.

Mini-form view 100 can be a visual display area that displays variousdisplay items. The visual display area can occupy an entire screen of adisplay device, a section of the display device (e.g., a window), or asection of a window (e.g., a pane).

Mini-form view 100 can include various sections. For example, section160 can be a main section of mini-form view 100. One or more images 152and 154 of various database forms can be displayed in an evenly spacedpattern (e.g., grid, table, list, etc.) in main section 160. In thisspecification, the term “database form” can be used to refer to a visualuser interface for displaying one or more data records. A database formcan include at least two conceptual components: data and layout. Thedata of the database form can be data retrieved from a database usingone or more queries. The data can include one or more data fields. Forexample, in an online auction database, the data fields can include“name,” “price,” “description,” etc. The layout of the database form canspecify an arrangement on how the data are displayed. The layout canspecify one or more data components, each data component correspondingto a data field in the data record. A database application developer canvisually arrange the data components in the layout such that varioustypes of data can be displayed at various positions. For example, datahaving an enumeration (enum) type can be displayed using a list. The“name” of an item being auctioned can be displayed in bold type; the“price” of the item can be displayed below the name; images can bedisplayed on fixed or variable image areas, etc.

Sometimes it is desirable to display multiple database forms in onesingle window or pane. However, depending on the number and complexityof the data components, a database form can occupy a large area of adisplay device. For example, image 152 can represent a database formcontaining numerous drop-down list, text, and graphics fields that, whendisplayed in the size specified in the layout, can occupy an entirescreen. When the display device is a screen on a mobile device, even anentire screen may be insufficient for displaying the database form. Aconventional database application program may attempt to solve theproblem by presenting a digest of the form. In a digest, parts of thedata record (e.g., a snippet of text, etc.), rather than all the text,are displayed. Furthermore, the digest can be displayed in a list ortable. Thus, the digest may not reflect the arrangement defined in thelayout of the form.

In main section 160, images 152 and 154 of database forms are displayed.Images 152 and 154 can be referred to as “mini-forms” to emphasis thatconceptually, images 152 and 154 can be database forms having a small(e.g., thumbnail) size. For example, the mini-forms can be snapshotimages of underlying database forms. Each of images 152 and 154 can havea different (e.g., reduced) size, compared to the original databaseforms they represent. For example, stripe 162 can represent a drop-downlist; wavy lines 164 can represent text; image 166 can be a thumbnail ofan original image, etc. Large-sized text (e.g., titles “Description” and“Reviews”) can be shown in reduced size. Therefore, multiple images 152and 154 of database forms can be displayed in a single window or panehaving limited display “real estate” (e.g., area for display).Furthermore, the size of each image can be adjustable. Images 152 and154 can be generated from the database forms automatically at varioustimes (e.g., at time the application program is launched, at time thedatabase is queried or updated, or at time that a user navigates to agroup of database items).

Images 152 and 154 can, but is not required to, be digital picturesgenerated from the underlying database forms. In some implementations,images 152 and 154 can be rendered by a graphic engine in a mannersimilar to rendering a regular form. For example, images 152 and 154 canbe generated based on a layout with reduced, but proportionaldimensions. In some implementations, images 152 and 154 can containsimplified content. For example, lines of text segments in the databaseforms can be represented as wavy lines in images 152 and 154. Thicknessof the lines can correspond to a font size; color of the lines cancorrespond to a font color; dashed lines can indicate italic orunderline font, and so on.

Images 152 and 154 each can be displayed in association with propertylabels 156 and 158, respectively. Property labels 156 and 158 can eachcorrespond to one or more parameters of the mini-forms. The content ofproperty labels 156 and 158 can be configurable. Further details onconfiguring property labels 156 and 158 will be described below inreference to FIG. 3B.

Mini-form view 100 can include folder section 142. Folder section 142can include various folders, e.g., icons, labels, or other userinterfaces that can specify various display items that are displayed onmain section 160. Each box in folder section 142 of FIG. 1A represents afolder or icon. By way of illustration, a folder labeled “My Library”can contain items (e.g., icons) labeled “Radio . . . ” and “MacBook . .. ” that correspond to images 152 and 154, respectively. Selecting thefolder labeled “My Library” can cause images 152 and 154 to be displayedin main section 160. If a user selects another folder, other imagescorresponding to the other folder will be displayed. Further details onfolder management will be described below in reference to FIGS. 2A-2C.

Mini-form view 100 can include control section 144 for allowing users tomanipulate content in main section 160. Control section 144 can includea filter selection interface 146 for filtering the content,configuration interface 148 that allows a user to configure variousproperties of the images 152 and 154, and image size control interface150 for control the sizes of the images. More details of the interfaces146, 148, and 150 will be discussed below in various sections of thisspecification.

FIG. 1B illustrates an exemplary mini-form view 180 of images offormatted data records where one data record is selected for editing.For convenience, folder section (e.g., folder section 142) or controlsection (e.g., control section 144) are omitted from mini-form view 180.

Mini-form view 180 can be divided into two sections, browse section 182and detail section 192. Various images (e.g., mini-forms) 184, 186, 188,and 190 are displayed in browse section 182. Images 184, 186, 188, and190 can be arranged in various ways in browse section 182. Thearrangement can be determined by the size of each image and the size ofbrowse section 182. Content of images 184, 186, 188, and 190 can includetext (shown as wavy lines) and pictures (shown in rectangles in each ofthe images).

A user can select one of the images 184, 186, 188, or 190. The systemcan indicate in various ways that a particular image (e.g., image 186)is selected. For example, a highlighted frame can be displayed aroundselected image 186. In some implementations, the system can force anitem (e.g., an item at the top-left position of a grid) to be selectedby default, if the user does not make an explicit selection.

Once an image is selected, the database form corresponding to the imagecan be displayed in detail section 192 of the screen. The form can bedisplayed in full-size (e.g., the original size as specified in thelayout). Furthermore, in some implementations, the form size can beadjustable. Therefore, a user can make a form as large or small as theuser wishes.

By way of illustration, a user selects image 186. The database formunderlying image 186 (e.g., the form based on which image 186 iscreated) can be displayed in detail section 192. Dropdown control 194,shown as stripe 187 in image 186, can be displayed in full size.Description text 196, shown as lines under stripe 197 in image 186, canbe displayed in font, color, and size as specified by the layout.Picture 198, shown as a thumbnail in image 186, can be displayed basedthe specific formatting information according to the layout.

Detail section 192 is shown in the same mini-form view 180 as browsesection 182, producing the visual effect of splitting mini-form view 180(a window or a pane) into two portions. In this specification, eachportion can be referred to as a viewport. Multiple viewports are not theonly way to display a browse section and a detail section. In someimplementations, the detail section can be displayed in a separatewindow, based on configuration or user preference.

In various implementations, images of database forms displayed in browsesection 182 can share a same layout, or each use a distinct layout. Inthe example shown, each of images 184, 186, 188, and 190 has a distinctlook (e.g., in terms of what data fields are displayed and how the datacomponents are arranged). Each of images 184, 186, 188, and 190 can begenerated using data from distinct queries, and formatted based on adistinct layout. By way of illustration, image 186 can correspond to a“for auction” item in the database, formatted using a layoutspecifically designed for “for auction” items (as opposed to, e.g., alayout for employee records).

Organizing Mini-Forms in Folders

FIGS. 2A-2C illustrate exemplary mini-form view of images of databaseforms that are organized in a hierarchical structure. The hierarchicalstructure can be created by a user (e.g., by putting documents intofolders, or by putting sub-folders into folders). The folders can bereferred to as having a higher level in an organizational hierarchy thanthe documents and sub-folders. The hierarchical structure can also bedetermined by system logic. For example, a layout can correspond to manydata records formatted using the layout. The layout can be referred toas having a higher level in the organizational hierarchy than thedatabase forms formatted using the layout.

FIG. 2A illustrates exemplary techniques for presenting multiple displayitems in a hierarchical structure on mini-form view 200A. Variousdisplay items can be grouped into a hierarchical structure in a library.For convenience, the term “library” can refer to an entire collection ofdisplay items in this specification. The library can be represented aslibrary folder 220 a in folder section 210 of mini-form view 200A.Display items in the library can be represented as icons in a sourcelist using library folder 220 a as a root folder. For convenience, theterm “icon” is used to describe representative entities in source listin folder section 210. An icon can be a small pictogram that representsan underlying display object. In various implementations, other forms ofrepresentations of display objects (e.g., text snippets or graphicsymbols) can be used in place of icons.

By way of illustration, the source list under library folder 220 a cancontain icons 230 a, 232 a, 234 a, 242 a, and 244 a. Each icon cancorrespond to a display item to be displayed in main section 212. Eachicon can be a folder containing other icons. For example, icon 232 a canbe a folder that contains icons 242 a and 244 a. The icons, as shown,are placed in three levels in the hierarchical structure. Forconvenience, library folder 220 a will be referred to as having a firstlevel (e.g., a root level); icons 230 a, 232 a, and 234 a will bereferred to as having a second level; icons 242 a and 244 a will bereferred to as having a third level.

A user can place a display item at any level in the hierarchy structure,including root level. For example, using a “drag and drop” feature, auser can reorganize the hierarchy structure by manipulating the icons inthe source list. The user can change the levels of or relationshipbetween the display items represented by the icons. By way ofillustration, the user can move icon 234 a under icon 232 a. The secondlevel display item represented by icon 234 a can have a third levelafter the move. Similarly, the user can move icon 242 a directly underlibrary folder 220 a. After the move, the third level display itemrepresented by icon 242 a can have a second level after the move.

In some implementations, display items can be organized based on theinternal logical relationship between the display items. For example,icon 232 a can represent a layout. Icons 242 a and 244 a can representimages of database forms formatted according to the layout. In someimplementations, an icon can correspond to a folder created as aplaceholder for organization purposes. The folder can, but is notrequired to, have its own display attributes. For example, icon 232 acan represent a folder that is a placeholder for display itemsrepresented by icons 242 a and 244 a.

Content displayed in main section 212 of mini-form view 200 a cancorrespond to icons selected in the source list. For example, when theuser selects library folder 220 a, display items 202 a, 204 a, and 206 acan be displayed. Display items 202 a, 204 a, and 206 a can correspondto icons 230 a, 232 a, and 234 a, respectively.

Display item 204 a can be represented by icon 232 a, which has twosub-items. When display item 204 a corresponds to a layout based onwhich database forms are formatted, display item 204 a can be an imageof the layout. When display item 204 a corresponds to a folder as aplaceholder, display item 204 a can be an image of a first itemcontained in the folder. For example, display item 204 a can be an imageof a database form that is represented by icon 242 a in the source list.

While viewing higher-level display items (e.g., second-level displayitems 202 a, 204 a, and 206 a), a user can access lower-level displayitems (e.g., third-level display items represented by icons 242 a and244 a) in various ways. In some implementations, display item 204 a canbe animated upon a user selection. The user can activate the animationby scrubbing display item 204 a (e.g., by sliding a pointing deviceacross at least a portion of display item 204 a). For example, the usercan move the pointing device according to the path indicated by thearrow across display item 204 a. The pointing device can be a cursorcontrolled by a mouse or a finger or a stylus moving across atouch-sensitive display screen, among others. In some implementations,the sliding motion over one particular display item can activate theanimation for that display item, while other display items remainunchanged.

The animation can include displaying images of display items in thelower level one after another, in a display area previously occupied bythe selected higher-level display item. For example, upon receiving auser selection, the screen area that displays display item 204 a canalternatively show a snapshot of database form as represented by icon242 a and a snapshot of database form as represented by icon 244 a. Eachof the two snapshots can be shown for a certain time period (e.g., aconfigurable number of seconds, also referred to as a refreshingfrequency), before the other one is shown, giving an appearance of aslide show.

In some implementations, the slide show can animate the snapshots usinga flipping action. In some implementations, the slide show can animatethe snapshots by scrolling a snapshot out of a display area whilescrolling another snapshot into the display area, mimicking a slidingmotion, according to the direction of movement of the pointing device.For example, upon receiving a cursor moving from left to right accordingto the arrow as shown over display item 204 a, the snapshot of databaseform as represented by icon 242 a can scroll to the right untildisappearing from display item 204 a. The snapshot of database form asrepresented by icon 244 a can scroll in until fully occupying the areaof display item 204 a. The scrolling motion can be repeated untilstopped by the user (e.g., by a click on a particular display item thatselects the display item). Once the scrolling motion has stopped, theselected display item (e.g., the display item represented by icon 244 a)can be restored.

While the screen area that displays display item 204 a is showing ananimated view of display items, display items 202 a and 206 a need notbe animated. However, each of display items 202 a and 206 a can beindividually animated (e.g., when the display items have lower-levelitems and are selected). The animation of display items 202 a and 206 acan, but need not, use the same refreshing frequency as applied todisplay item 204 a. In some implementations, a user can activateanimations on multiple display items. For example, a user can selectmultiple display items (e.g., by drawing a bounding box around thedisplay items). When the user slides a pointing device across one of theselected display items, animation can start for each selected displayitems.

FIG. 2B illustrates exemplary techniques for receiving user inputselecting a particular display item among multiple display items in ahierarchical structure on a mini-form view 200 b. Display items 202 band 206 b can be images of database forms. By way of illustration,display item 204 b is being animated. Various icons 220 b, 230 b, 232 b,242 b, 244 b, and 234 b are shown in a source list. In someimplementations, during animation, icons representing the currentlydisplayed display item can be emphasized (e.g., by highlighting). Forexample, as display item 204 b cycles through images of database forms,icons 242 b and 244 b can be alternatively highlighted.

As images cycle through display item 204 b, a user can select aparticular image being displayed. For example, at time an imagerepresented by icon 242 b is displayed as display item 204 b, the usercan perform a selection act (e.g., click, right-click, or tap, dependingon type of the display device) on the image or the icon 242 b (which canbe highlighted) to select the display item. The selection act can pausethe animation at the selected mini-form.

FIG. 2C illustrates an example mini-form view 200 c after a user selectsa particular mini-form among multiple display items (which can includemini-forms and other content). For convenience, folder section 210 isomitted from mini-form view 200 c. Display items 202 c and 206 c can beimages of database forms. Display item 204 c has been cycling throughtwo images of data records from an auction item database. At time adisplay item was displayed (e.g., a mini-form represented by icon 242b), the user pauses the display item. The user double-clicks (or taps)on the paused display item. New window 210 appears (according to aconfiguration that specifies that a new window, instead of a viewport,will be used). The database form underlying the mini-form (e.g., aformatted record for a radio scanner being auctioned) is shown in newwindow 210.

In addition to displaying formatted data, a database form can be used toaccept user inputs into the database. For example, in window 210,various text sections 213 and 214, selection sections 216 and 218, andimage 220 can be modified, if the user has access privilege to performthe modifications. The modifications can be communicated to the databaseto update corresponding data tables.

FIG. 2D illustrates an exemplary mini-form view 200 d of images of datarecords in shared databases. Mini-form view 200 d can include multipledisplay objects 262, 264, and 266. Each of display objects 262, 264, and266 can correspond to a form or other object in a shared database (e.g.,shared database 272, 274, or 276). Shared databases 272, 274, and 276can be hosted locally or remotely.

Various objects, including libraries or formatted data records, can beshared among multiple users using multiple computing devices incommunications network 270. Sharing can include a user designating oneor more libraries, folders, database forms, or collection of items ofthe user to be viewable by other users using other computing devices. Byway of illustration, a user (user A) can share database 272, accessshared database forms of shared database 274 created by another user(user B), and access shared library of shared database 276 created byanother user (user C). By way of illustration, mini-form view 200 dshows a view for user A.

User A can share display items on which user A has access andmodification privileges (e.g., items that user A owns). User A canaccess a local database or database 272 through communications network270, create one or more layouts, create one or more database forms usingthe layouts, and share the database forms by designating at leastanother user (user B) who can access the database forms through network270. User B can include one or more individual users, one or more groupsof users (e.g., users in “friends” or “colleagues” user groups),everyone in a particular network (e.g., an internal network), or generalpublic, etc. By sharing the database forms, user A can allow user B toview the database forms in various mini-form views. Sharing the databaseforms with user B can grant user B access privileges to shared database272. The access privileges can be limited to the database forms beingshared (e.g., access to other database tables or records that are notrelated to the shared items can be denied). The access privileges caninclude read-only (e.g., user B can see a “preview” of a newly designedlayout), read-and-write (e.g., user B can modify the data underlying theshared form), or share (e.g., user B can share the shared database formswith other users). Display item 262, as shown in main section 212, canbe an image of user A's library, or a mini-form of one of the shareddatabase forms.

User A can access user B's shared database forms. User B can share oneor more database forms stored on a database 274. Display item 264 can bea mini-form of one of the database forms shared by user B. Depending onwhat access privileges are granted to user A, user A can view, edit, orshare the shared database forms with other users. In someimplementations, user B can require user A to enter a user name, apassword, or both before database forms are displayed to user A.

User A can access user C's shared library. User C can share a library ofshared database 276. The library can include database forms and otherdisplay items (e.g., images, video clippings, etc.). The library ofshared database 276 is shown as display item 266 on main section 212 ofmini-form view 200 d. User A can view display items contained in theshared library, for example, by scrubbing across display item 262 (e.g.,by moving a pointing device across display item 262). If the librarycontains more than one database forms, display item 266 can, by default,display a mini-form of the first database form in the library. In someimplementations, when display item 262 corresponds to a library, imageproperty fields under display item 266 can contain information on howmany items there are in the library.

In some implementations, a mini-form for a library can be distinguishedfrom non-library mini-forms by a title header. A layout can specify atitle header for a form. A title header can be information that appearsat a top section of a database form. When displaying a data record as amini-form, the title section can be omitted in order to optimize thedisplay (e.g., by maximizing the amount of information displayed fordata rather than for title). When displaying a library as a mini-form(e.g., by displaying the first database form in the library), the titlesection can be preserved, because the title can be a common element ofall database forms in the library. For example, display item 266 caninclude the title in the database forms (e.g., “C's Auction”).

Folder section 210 of mini-form view 200 d can contain icons 252, 254,and 256, which can represent display items 262, 264, and 266,respectively. Icons 258 and 260, which are shown as sub-items of icon256, can represent display items contained in shared library of shareddatabase 276. Folder section 210 can be populated when the user opensgrid view 200 d. A back-end engine can perform a search in a designatednetwork (e.g., a corporate intranet, a subnet, or a workgroup) andlocate shared libraries and database forms. The back-end engine cangenerate a collection of icons for the found libraries, shared databaseforms, and other shared display items. For a shared library or a shareddatabase form that is protected by password, security status indicator255 (e.g., a lock) can be displayed alongside the icon. When the userenters a valid password, security status indicator 255 can be changed(e.g., to an unlocked state), or be removed from display.

Folder section 210 and main section 212 of mini-form view 200 d can beupdated in response to a change in shared items over network 270.Mini-form view 200 d can automatically response to remote actions. If alibrary is added to a database in a designated network (e.g., a companyintranet), of if a library's attribute is changed from “not shared” to“shared”), a user viewing that database's shared libraries can see thenew (or newly shared) library appearing automatically. For example, thenew library can appear in both folder section 210 (represented by anicon) and main section 212 of mini-form view 200 d (shown as amini-form). Conversely, if a shared library is deleted, or the attributeis changed from “shared” to “not shared,” folder section 210 and mainsection 212 will be updated accordingly.

Configuring Exemplary Mini-Form View

FIGS. 3A-3C illustrate exemplary user interfaces for configuring amini-form view display of images of database forms. FIG. 3A illustratesexemplary mini-form view 300 a. Mini-form view 300 a can include controlsection 144, which can include configuration interface 148 and imagesize interface 150. For clarity purposes, other control interfaces arenot shown. By way of illustration, display items 302, 304, and 306 areshown. Each of display items 302, 304, and 306 can be an image of adatabase form. Display item 304 is shown to have double frame toillustrate the fact that display item 304 is an active item beingconfigured.

FIG. 3B illustrates exemplary mini-form view 300 b in which image 304 isbeing configured. A user can configure display item 304 by activatingconfiguration interface 148. For example, the user can click onconfiguration interface 148 using a mouse click or tap on configurationinterface 148 on a touch-sensitive screen. Upon activation,configuration panel 308 can be displayed in mini-form view 300 b.Configuration panel 308 can include active display item 304, and one ormore label fields 310, 312, 314, and 316.

Label fields 310, 312, 314, and 316 can be utilized to describe displayitem 304. Label fields 310, 312, 314, and 316 can each correspond to asource data field in the data record underlying display item 304. Forexample, label field 310 can show a name; label field 312 can be show aprice (e.g., of an item being auctioned); label field 314 can show adate; and label field 316 can be empty (e.g., “None”). By activating ascroll button on each of the label fields, a list of eligible datafields can be shown.

In some implementations, configuration panel 308 can be transparent orsemi-transparent. Other display items entirely or partially covered byconfiguration panel 308 (e.g., display items 302 and 306) can be visiblethrough configuration panel 308. The portions of the display items beingcovered can be shown in darker brightness. The user can close displaypanel 308 by various ways (e.g., clicking on configuration interface 148again, or clicking on another portion of mini-form view 300 b other thandisplay panel 308).

Once the user selects a source data field for a label field, the valueof the data field can be displayed in an image property label. Forexample, the value of “name” field 310 can be “Radio Scanner;” the valueof the “price” field 312 can be “$500;” the value of the “date” field314 can be “September 9.” Once display panel 308 is closed, display item304 will have an image property label corresponding to the name, price,and date (e.g., image property label 156). Image property label 158 canbe similarly configured.

FIG. 3C illustrates an exemplary mini-form view 300 c in which displaysize of each display item is adjustable. Each display item 304 or 304can be a thumbnail image of a database form having a dimension of m×npixels. A thumbnail can have a size that is sufficiently large such thatmajor characteristics of the underlying database form can berecognizable. Depending on the size of each display item, mini-form view300 c can contain more or fewer display items that are visible. In someimplementations, the size of all display items can be adjusted inuniform. In some implementations, the size of each display item can beadjusted individually.

A user can adjust the size of each display item 302 or 304 using imagesize control interface 150. Image size control interface 150 can be aslide control interface that includes a groove and slider. A user can“grab” the slider (e.g., by click-and-hold on the slider using a mousedevice, or by touching the slider using a finger or stylus on atouch-sensitive screen) and move the slider along the groove. Moving theslider to one direction (e.g., left) can cause the display item 302 and304 to be displayed in smaller sizes; moving the slider to anotherdirection (e.g., right) can cause the display item 302 and 304 to bedisplayed in larger sizes.

Image size control interface 150 can have other forms in addition tobeing a slide control interface. For example, image size controlinterface 150 can include a knob that can be turned, buttons with labelsor icons, or any other mechanism.

FIG. 4A illustrates an exemplary mini-form view 400 of images ofdatabase forms (e.g., mini-forms) displayed together with other content.Mini-form view 400 can include heterogeneous display items havingvarious source, genre, and form. For example, display item 406 caninclude a digital picture; display item 408 can include a digital videoclip; and display item 410 can include an image of a formatted datarecord. Display items 406, 408, and 410 can be displayed on a same mainsection 404 of mini-form view 400.

A user can determine which display items can be included in mini-formview 400 by way of filter selection interface 146. Filter selectioninterface 146 can be one of the controls in control section 144 ofmini-form view 400. Filter selection interface 146 can include adropdown list 402, listing which item can be displayed. By way ofillustration, dropdown list 402 can include entries “Show All,”“Document,” “Image,” “Video,” and “Forms.” A user can select one or moreentries from dropdown list 402. If selected, the particular genre ofdisplay items (e.g., mini-forms, under entry “Forms”) can be displayed,while unselected genre of display items can be hidden from display.Selecting “Show All” can turn off the filter and display all genres ofdocuments.

FIG. 4B illustrates an exemplary user interface for creating a libraryof images of database forms from mini-form view 420. Mini-form view 420can include folder section 422 and main section 423. Mini-form view 420can include multiple display items (e.g., display items 434, 436, 438,and 440, among others). Each solid-bordered box in main section 423represents a display item.

As described above, display items can be organized in a hierarchicalstructure. The hierarchical structure can have a root item and varioussub-items. Each sub-item can include other sub-items. For example, thehierarchical structure can include root folder 424 (e.g., a libraryfolder) that contains various sub-items 426, 428, 430, and 432. A usercan create the hierarchical structure in various ways. For example, theuser can use a drag-and-drop operation to put one or more display itemsone level under another display item in the hierarchy.

By way of illustration, the user can select display items 434, 436, 438,and 440 by drawing bounding box 442 around display items 434, 436, 438,and 440. Display items 434, 436, 438, and 440 can be highlighted whenselected (e.g., each of display items 434, 436, 438, and 440 can have ahighlighted border). The user can drag bounding box 442 and dropbounding box 442 under library folder 424. Upon the drop, icons 426,428, 430, and 432 can be created, the icons corresponding to displayitems 434, 436, 438, and 440, respectively. Similarly, the user canselect, drag, and drop display items 434, 436, 438, and 440 into anon-root level folder.

To be placed into a same folder, display items 434, 436, 438, and 440need not be homogeneous. Display item 434 can be an image of a databaseform, display item 436 can be a layout under which multiple databaseforms are included, and so on.

Library folder 424 can have a label “My Items,” which can be editable bya user. Each of icons 426, 428, 430, and 432 can also be associated witha label. In some implementations, the label can be a label created foran image of formatted data record, e.g., an image property label asdescribed above with reference to FIG. 1A.

Exemplary Processes for Displaying Data Records in Mini-Form View

FIG. 5A is a flowchart illustrating an exemplary process 500 ofdisplaying data records in mini-form view. For convenience, exemplaryprocess 500 will be described in reference to a system that implementsexemplary process 500.

The system can construct (502) a formatted view (e.g., a database form)of a data record. The data in the formatted view can be retrieved from alocal or remote database by one or more queries. The data record can,but is not required to, correspond to one single row of data in adatabase table. The data record can include one or more data fields. Theformat of the formatted view can be determined by a layout. The layoutcan define the arrangement that can represent a way information isorganized and presented when a user browses, previews, or prints thedata record. For example, the layout can include an arrangement of thedata components on display, each data component corresponding to a datafield. Various data components (e.g., data, objects, pictures, and otherlayout parts) having various configurations can be position on a displayaccording to the arrangement. An application developer can designdifferent layouts for entering data, printing reports and mailinglabels, displaying web pages, and so on.

The layout of stage 502 can specify a size of the formatted view. Forconvenience, the size of the formatted view as specified in the layoutwill be referred to as an original size of the formatted view. Theoriginal size can be explicitly defined in number of pixels, measurementunits (e.g., inches or centimeters), percentage of a width and height ofa window, etc. In some implementations, the original size need not bespecified explicitly in the layout. Size of the data components canimplicitly determine the original size of the formatted view. Forexample, the layout can specify a font size for text fields and labels,a dimension for pictures, and an arrangement that defines how far apartone data component is displayed from another data component. Theoriginal size of the formatted view can be determined by a bounding boxthat includes all data components. Constructing the formatted view caninclude rendering the retrieved data record in computer memory using thelayout.

The system can create (504) one or more images (e.g., mini-forms)corresponding to the formatted view. An image can be an actualelectronic graph (e.g., a picture in Graphics Interchange Format (GIF)or any other format), or a version of the formatted view that having asize (e.g., a thumbnail size) that is distinct from the original size.In the latter case, in some implementations, a user can directly inputdata in the thumbnail-sized form. The image can preserve the arrangementof the data components specified in the layout. For example, therelative positions of the data components in the image can remain thesame as the relative positions of the data components in the formattedview. However, the size of the data components and the distances betweenthe data components can be scaled proportionally, such that the datacomponents can by displayed on a smaller display area than originallydesigned.

The system can display (506) the image of the formatted view on adisplay device. The image can be displayed with other images offormatted views, as well as with other content item (e.g., pictures,video, text snippets, etc.). Each image or other content item can bereferred to as a display item. The display items can be arranged invarious display patterns. Some example patterns are described below withrespect to FIGS. 5C-5F.

Optionally, the system can receive (508) a user selection of an image ofa formatted view. The user selection can be an input that can include,for example, a single or double click on the image using a pointingdevice (e.g., a mouse), a tap on the image on a touch-sensitive screenusing a finger or a stylus, or using a configurable key combination on akeyboard device.

Upon receiving the user selection, the system can display (510) theformatted view corresponding to the selected image in a display area.The formatted view can be displayed in a display size that is differentfrom the image size (e.g., in a bigger size). The display area can be aseparate viewport (e.g., a pane section on a display window), a newwindow, a full screen, etc. The display size of the formatted can be theoriginal size specified in the layout, or another size such that text inthe formatted view is intelligible and input fields are sufficientlylarge that the user can enter text, selections, checkmarks, etc. inorder to modify data components.

Optionally, the system can receive (512) an input from the display area.The input can include a user modification of data in one or more of thedata components of the formatted view. The modification can includeentering or modifying text in a text field, adding, updating, ordeleting a picture, making a selection, etc.

The system can update (514) the data record represented by the formattedview in response to the input. Updating the data record can includeinserting, modifying, or deleting one or more data records, orinserting, modifying, or deleting a value of a field. Updating the datarecord can further include committing (e.g., pushing) the changes intothe database

The system can propagate (516) the updated data record to other displayitems. As described above, other display items can be images of databaseforms as well as other content. When a display item is an image ofanother database form, a change in the data record being modified canhave a rippling effect on other data records. Changes other thanupdating data records can cause display items to be updated. Forexample, multiple mini-forms being displayed can change when a databaseschema changes or when the layout underlying the mini-forms changes(e.g., when display component changes size or position).

By way of illustration, a database table can include sales informationfor car dealerships. A layout can specify that a data field “salesamount in dollars” for dealerships shall be formatted in bold font andred color if the amount for a particular dealership is the highest amongall dealerships. For other sales amounts, the data field can bedisplayed in normal font in black color. At the time images for variousdatabase forms are generated, the form for dealership A can show thesales amount value in bold font and red color (because A has the highestamount in sales). The image for the form for A can show a value amountin bold and red, even though the actual text in the image may not beintelligible due to the image's small size. For example, a red dash canbe displayed in the image in place of the actual text. The user selectsimage A. A full-sized form for dealership A can be displayed in adisplay area (e.g., a split pane of a display window). The user can editthe sales amount value in the full-sized form. The user can type in anew and lower sales amount. After the change, dealership B can have thehighest sales amount. The user saves the form. The system can update thedata records. The system can propagate (516) the changes to the imagefor dealership B. As a result, the image for dealership B can change. Athin, black dash that represents a sales amount can be replaced by athick, red dash.

For another example, the database forms each can contain a global datafield (e.g., a company icon). If a user changes the company icon in onedatabase form, the system can propagate (516) the change and regenerateimages for other database forms, such that all images displayed onscreen includes the new icon.

FIG. 5B is a flowchart illustrating an exemplary process 520 ofdisplaying images of data records that are organized in a hierarchicalstructure. For convenience, exemplary process 520 will be described inreference to a system that implements exemplary process 520.

The system can acquire (522) a library of display items. The displayitems can be organized into two or more levels. By way of illustration,two levels are used, and referred to as a first level and a secondlevel. The terms “first” and “second” are used to indicate a distinctionbetween the two levels. The library can contain various display items(e.g., database forms, images of database forms, digital pictures,documents, and folders). The display items can include images offormatted views (e.g., mini-forms), each formatted view including one ormore data records formatted according to a layout.

The system can display (524) one or more display items having afirst-level according to a display pattern (e.g., a grid pattern) in adisplay area. The formatted view can have a first level based on userdefinition or intrinsic logic. For example, a first display item cancorrespond to a layout that defines display arrangements of one or moredata components. The first level can be, but is not limited to, a rootlevel or level that is directly below a root level.

The system can receive (526) a selection of one or more first-leveldisplay items. The selection can include moving across at least aportion of a first-level display item using a pointing device. Thepointing device can include a cursor controlled by a mouse device, afinger or stylus gesturing on a touch-sensitive screen, or any otherinput device that can track motion. The selection can also made by keycombination on a keyboard device. The selected display item cancorrespond to one or more of second-level display items. For example,the second-level display items can correspond to data records formattedaccording to the layout. The display data records can each include oneor more data fields that correspond to the various data components.

The system can animate (528) the selected display item in response tothe selection. Animating the selected display item can includedisplaying the second-level formatted display items that correspond tothe first-level display item in the display area occupied by thefirst-level display item. The animation can occur at a display positionthat corresponds to the first-level display item, such that content ofthe first-level display item appears to be changing as a slide show.Other first-level display items need not be animated. However, eachfirst-level display item can be animated individually, independent ofother first-level display items. The animation can include iteratingthrough the second-level display items, and displaying each of thesecond-level display item for a given amount of time, then displayinganother image of second-level display item. The iteration can berepeated until interrupted (e.g., stopped by a user).

FIGS. 5C-5F illustrate exemplary display patterns of images of formatteddata records. By way of illustration, a grid pattern, a stripe pattern,a stack pattern, a carousel pattern are shown. Other display patternscan be used. A user can select a display pattern among a variety ofpre-configured or user-defined display patterns.

FIG. 5C illustrates an exemplary grid display pattern 530 for displayingvarious display items. In grid display pattern 530, display items 532can be shown in a grid view, e.g., evenly spaced on a grid with orwithout gridlines. Display items 532 a, 532 b, 532 c, 532 d, 532 e, and532 f can each represent an image of a formatted data record (e.g.,database forms), a picture, a part of a document, or other displaycontent.

FIG. 5D illustrates an exemplary stripe display pattern 540 fordisplaying various display items. In stripe display pattern 540, displayitems 544 a, 544 b, and 544 c can be shown linearly (horizontally orvertically). Buttons 542 a and 542 b can be provided for scrolling thelinear stripe. Other scrolling controls can be provided as well. Forexample, a slide bar can be used. Scrolling control can also include atouch-sensitive display device. A user can gesture using a finger or astylus in order to control the scrolling.

FIG. 5E illustrates an exemplary stack display pattern 550 fordisplaying various display items. In stack display pattern 550, thedisplay items can be stacked upon each other (e.g., one display itemfully or partially overlaps another). Display item 552, which is notcovered by another display item, can be referred to as a top displayitem. The display items can each be moved to the top using a flip actionor a parade action. For example, top display item 552 can move to thebottom of the stack in an animated fashion, and the second-top displayitem can move to the top in a forward parade. The display items can alsomove in a backward parade, upon a user command.

FIG. 5F illustrates an exemplary carousel display pattern 560 fordisplaying various display items. In carousel display pattern 560,display items 562 a, 562 b, 562 c, 562 d, 562 e, and other display itemscan be arranged in a circle, the whole or part of the circle can beshown on a display screen. A user can navigate through the display itemsby turning the circle (e.g., by a click and drag using the mouse, or bya strike of a pointing device on a touch-sensitive display device,etc.). Upon receiving a user input to turn the circle, the display items562 can be animated to simulating a turning motion around a center.

Exemplary System Architecture

FIG. 6 is a block diagram of an exemplary system architecture 600 forimplementing the features and operations described in reference to FIGS.1-5. Other architectures are possible, including architectures with moreor fewer components. In some implementations, architecture 600 includesone or more processors 602 (e.g., dual-core Intel® Xeon® Processors),one or more output devices 604 (e.g., LCD), one or more networkinterfaces 606, one or more input devices 608 (e.g., mouse, keyboard,touch-sensitive display) and one or more computer-readable mediums 612(e.g., RAM, ROM, SDRAM, hard disk, optical disk, flash memory, etc.).These components can exchange communications and data over one or morecommunication channels 610 (e.g., buses), which can utilize varioushardware and software for facilitating the transfer of data and controlsignals between components.

The term “computer-readable medium” refers to any medium thatparticipates in providing instructions to processor 602 for execution,including without limitation, non-volatile media (e.g., optical ormagnetic disks), volatile media (e.g., memory) and transmission media.Transmission media includes, without limitation, coaxial cables, copperwire and fiber optics.

Computer-readable medium 612 can further include operating system 614(e.g., Mac OS® server, Windows® NT server), network communication module616, database interface 620, database server 630, database applicationprogram 640, and libraries 650, as described in reference to FIGS. 1-5.Operating system 614 can be multi-user, multiprocessing, multitasking,multithreading, real time, etc. Operating system 614 performs basictasks, including but not limited to: recognizing input from andproviding output to devices 606, 608; keeping track and managing filesand directories on computer-readable mediums 612 (e.g., memory or astorage device); controlling peripheral devices; and managing traffic onthe one or more communication channels 610. Network communicationsmodule 616 includes various components for establishing and maintainingnetwork connections (e.g., software for implementing communicationprotocols, such as TCP/IP, HTTP, etc.). Database server 630 can host oneor more databases on a file system. The databases can be organized undera hierarchical folder structure, the folders mapping to directories inthe file system. Database application program 640 can perform variousfunctions for viewing data records, including formatting one or moredata records in a result set according to a layout. Libraries 650 caninclude one or more display items or references to display items under ahierarchical structure.

Architecture 600 can be included in any device capable of hosting adatabase application program. Architecture 600 can be implemented in aparallel processing or peer-to-peer infrastructure or on a single devicewith one or more processors. Software can include multiple softwarecomponents or can be a single body of code.

The described features can be implemented advantageously in one or morecomputer programs that are executable on a programmable system includingat least one programmable processor coupled to receive data andinstructions from, and to transmit data and instructions to, a datastorage system, at least one input device, and at least one outputdevice. A computer program is a set of instructions that can be used,directly or indirectly, in a computer to perform a certain activity orbring about a certain result. A computer program can be written in anyform of programming language (e.g., Objective-C, Java), includingcompiled or interpreted languages, and it can be deployed in any form,including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment.

Suitable processors for the execution of a program of instructionsinclude, by way of example, both general and special purposemicroprocessors, and the sole processor or one of multiple processors orcores, of any kind of computer. Generally, a processor will receiveinstructions and data from a read-only memory or a random access memoryor both. The essential elements of a computer are a processor forexecuting instructions and one or more memories for storing instructionsand data. Generally, a computer will also include, or be operativelycoupled to communicate with, one or more mass storage devices forstoring data files; such devices include magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; andoptical disks. Storage devices suitable for tangibly embodying computerprogram instructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, such as EPROM,EEPROM, and flash memory devices; magnetic disks such as internal harddisks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, ASICs (application-specific integrated circuits).

To provide for interaction with a user, the features can be implementedon a computer having a display device such as a CRT (cathode ray tube)or LCD (liquid crystal display) monitor for displaying information tothe user and a keyboard and a pointing device such as a mouse or atrackball by which the user can provide input to the computer.

The features can be implemented in a computer system that includes aback-end component, such as a data server, or that includes a middlewarecomponent, such as an application server or an Internet server, or thatincludes a front-end component, such as a client computer having agraphical user interface or an Internet browser, or any combination ofthem. The components of the system can be connected by any form ormedium of digital data communication such as a communication network.Examples of communication networks include, e.g., a LAN, a WAN, and thecomputers and networks forming the Internet.

The computer system can include clients and servers. A client and serverare generally remote from each other and typically interact through anetwork. The relationship of client and server arises by virtue ofcomputer programs running on the respective computers and having aclient-server relationship to each other.

A number of implementations of the invention have been described.Nevertheless, it will be understood that various modifications can bemade without departing from the spirit and scope of the invention. Forexample, the terms “database forms” and “mini-forms” are used. The it isnot a requirement that the forms or mini-forms must be connected to adatabase. Any formatted view of data is included in the scope of thisspecification. Accordingly, other implementations are within the scopeof the following claims.

What is claimed is:
 1. A computer-implemented method, comprising:receiving, from a formatted view of a data record, a user input forconfiguring a display property of a representation of the data record,the data record being stored in a database and including one or moredata fields: providing for display a configuration panel overlaid on therepresentation of the data record, the configuration panel beingtransparent or semi-transparent, wherein the representation of the datarecord is visible through the configuration panel, and wherein theconfiguration panel includes one or more label fields, each label fieldcorresponding to a data field of the represented data record; receiving,through at least one of the one or more label fields in theconfiguration panel, a selection input selecting a corresponding datafield; and in response to the selection input, designating contentstored in the corresponding data field as the display property forpresenting the data record in the formatted view.
 2. The method of claim1, wherein the display property is a display label.
 3. The method ofclaim 1, wherein the configuration panel covers the representation ofthe data record and fully or partially covers one or morerepresentations each representing another data record, the one or morerepresentations being visible through the transparent orsemi-transparent configuration panel.
 4. The method of claim 1,comprising receiving a closing input closing the configuration panel,the closing input comprising one of: a click or touch input on theconfiguration panel, or a click or touch input outside of theconfiguration panel.
 5. A method comprising: presenting a plurality ofitems for display in a carousel display pattern, wherein the items arearranged in a circle, at least a portion of the items as arranged in thecircle being visible on a display device; receiving a navigation inputthrough the visible items, the navigation input comprising a draggingmotion on at least one visible item to turn the circle; and in responseto the navigation input, animating the visible items to simulate aturning motion around a center of the circle.
 6. The method of claim 5,wherein each item includes an image of a formatted data records.
 7. Themethod of claim 5, wherein the navigation input includes a click anddrag of a mouse device or pointing device on a touch-sensitive display.8. A system, comprising: one or more processors; and a non-transitorystorage device storing computer instructions operable to cause the oneor more processors to perform operations comprising: receiving, from aformatted view of a data record, a user input for configuring a displayproperty of a representation of the data record, the data record beingstored in a database and including one or more data fields: providingfor display a configuration panel overlaid on the representation of thedata record, the configuration panel being transparent orsemi-transparent, wherein the representation of the data record isvisible through the configuration panel, and wherein the configurationpanel includes one or more label fields, each label field correspondingto a data field of the represented data record; receiving, through atleast one of the one or more label fields in the configuration panel, aselection input selecting a corresponding data field; and in response tothe selection input, designating content stored in the correspondingdata field as the display property for presenting the data record in theformatted view.
 9. The system of claim 8, wherein the display propertyis a display label.
 10. The system of claim 8, wherein the configurationpanel covers the representation of the data record and fully orpartially covers one or more representations each representing anotherdata record, the one or more representations being visible through thetransparent or semi-transparent configuration panel.
 11. The system ofclaim 8, the operations comprising receiving a closing input closing theconfiguration panel, the closing input comprising one of: a click ortouch input on the configuration panel, or a click or touch inputoutside of the configuration panel.
 12. A system, comprising: one ormore processors; and a non-transitory storage device storing computerinstructions operable to cause the one or more processors to performoperations comprising: presenting a plurality of items for display in acarousel display pattern, wherein the items are arranged in a circle, atleast a portion of the items as arranged in the circle being visible ona display device; receiving a navigation input through the visibleitems, the navigation input comprising a dragging motion on at least onevisible item to turn the circle; and in response to the navigationinput, animating the visible items to simulate a turning motion around acenter of the circle.
 13. The system of claim 12, wherein each itemincludes an image of a formatted data records.
 14. The system of claim12, wherein the navigation input includes a click and drag of a mousedevice or pointing device on a touch-sensitive display.
 15. Anon-transitory storage device storing instructions operable to cause oneor more processors to perform operations comprising: receiving, from aformatted view of a data record, a user input for configuring a displayproperty of a representation of the data record, the data record beingstored in a database and including one or more data fields: providingfor display a configuration panel overlaid on the representation of thedata record, the configuration panel being transparent orsemi-transparent, wherein the representation of the data record isvisible through the configuration panel, and wherein the configurationpanel includes one or more label fields, each label field correspondingto a data field of the represented data record; receiving, through atleast one of the one or more label fields in the configuration panel, aselection input selecting a corresponding data field; and in response tothe selection input, designating content stored in the correspondingdata field as the display property for presenting the data record in theformatted view.
 16. The non-transitory storage device of claim 15,wherein the display property is a display label.
 17. The non-transitorystorage device of claim 15, wherein the configuration panel covers therepresentation of the data record and fully or partially covers one ormore representations each representing another data record, the one ormore representations being visible through the transparent orsemi-transparent configuration panel.
 18. The non-transitory storagedevice of claim 15, the operations comprising receiving a closing inputclosing the configuration panel, the closing input comprising one of: aclick or touch input on the configuration panel, or a click or touchinput outside of the configuration panel.
 19. A non-transitory storagedevice storing instructions operable to cause one or more processors toperform operations comprising: presenting a plurality of items fordisplay in a carousel display pattern, wherein the items are arranged ina circle, at least a portion of the items as arranged in the circlebeing visible on a display device; receiving a navigation input throughthe visible items, the navigation input comprising a dragging motion onat least one visible item to turn the circle; and in response to thenavigation input, animating the visible items to simulate a turningmotion around a center of the circle.
 20. The non-transitory storagedevice of claim 19, wherein each item includes an image of a formatteddata records.
 21. The non-transitory storage device of claim 19, whereinthe navigation input includes a click and drag of a mouse device orpointing device on a touch-sensitive display.